### AIM Considerations

AIM mode cannot be enabled when the browser is not in focus.

AIM maintains dialpad control while loading one, or multiple, new Web pages as long as the accesskey attribute is part of the page.

When a user presses a Dialpad button, or “access key,” the browser launches a URL without displaying any characters to the user. The button press information is sent to the URL and the Web page author returns subsequent screens. What the user views is up to the page author. Access key supplies the mechanism to capture button press information and send that information to a Web server.

The user is automatically in AIM when the page loads (attribute=accesskey) and can begin pressing Dialpad buttons to send button press information. As an example, you may want to have a link from your Home page to the AIM application or wherever else such a link makes sense.

When a user clicks a button that has not been mapped to a URL and the browser is in AIM mode, nothing happens.

Having a Clear softkey on the AIM page allows a user to clear previous search results and start a new search. The page author must set up a Clear softkey that loads the first AIM page to allow this action.

The Web pages resulting from Dialpad button presses are part of the history stack. This is normal browser behavior.

AIM is re-enabled when the phone goes back on-hook and the current Web page has valid access keys.

An error beep sounds if the user presses any Dialpad buttons while a new page is loading.

If the accesskey attribute is on the page, then:

- Text Entry/Editing (TE) softkeys do not appear when the user is in AIM. AIM does not have the default Text Editing softkeys such as alpha, backwards, etc.
- The <a> and <anchor> links that would normally appear on the screen are hidden.
- Normal text entry (<input> tags) is prohibited because it cannot co-exist with access keys. If, by error, regular Text Entry and access keys are on the same page, AIM rules take precedence. This means when the accesskey attribute appears on a page, the regular text entry (TE) softkeys do not appear.
- If the user enters the AIM Application, and there is an input field for TE, the field will not get focus. Focus does not occur, regardless of how many times the user selects the Line button next to the TE input field. Since TE is prohibited when access keys are present on a page, TE does not get focus.
- The server must send back a resulting page with the access keys for each Dialpad button in the page. Doing so maintains AIM across pages and retains dialpad ownership. The URLs associated with each accesskey can differ from the starting page in case the proxy server caches Web pages.

For example, after the page with access keys loads and the user pushes the dialpad, the Web server launches the URL:

    <a href="http://URL2" accesskey="2">2<\a>

In the resulting page, the page author can send a different URL to be associated with the same access key:

    <a href="http://URL2a" accesskey="2">2<\a>